The minimum required hardware specification for the Director setup should be:
For Fabric Servers and API Server/Director Console:
Component |
Requirement |
|---|---|
Number of vCPU |
Minimum 4 |
RAM |
Minimum 8 GB |
HDD |
Minimum 100 GB |
For LPSM:
Component |
Requirement |
|---|---|
Number of vCPU |
Minimum 2 |
RAM |
Minimum 8 GB |
HDD |
Minimum 100 GB |
For Fabric-enabled LogPoint instances:
Component |
Requirement |
|---|---|
Number of vCPU |
Minimum 4 |
RAM |
Minimum 8 GB |
HDD |
Minimum 100 GB |
Note
All components of the Director setup must be installed in a Virtual Environment.
Depending on log volume, hardware requirements are subject to change.
The ZFS (Zettabyte File System), used in the LogPoint Director, itself provides a software-defined solution for disk-based redundancy (Mirror, RAIDZ). Hence, it is not recommended to use hardware-based RAID. Doing so limits the ZFS to perform self-healing on checksum failures.
When selecting the RAIDZ mode, the first three disks are used for OS and Application installation. The remaining disks, if any, can be used to extend the disk space or used as L2ARC (Level 2 Adjustable Replacement Cache) or ZIL (ZFS Intent Log) for enhancing the read/write performance of ZFS. This can be done using ZFS commands.
The following browsers best support LogPoint Director components:
Safari (latest)
Google Chrome (latest)
Firefox (latest)
To establish a connection within or outside the Director setup when using a network firewall:
Description |
Ports required |
|---|---|
Connection from Director components to other servers (NTP, DNS, and for support connection) |
|
Connection between the Fabric Servers (in a cluster setup) |
|
Connection from the Fabric Server to the API Server, LPSM or LogPoint |
|
Connection from the API Server to the Fabric Server |
|
Connection from the LPSM to the Fabric Server |
|
Connection from the LogPoint to the Fabric Server |
|
Access to LPSM UI, Director Console API, and Director Console UI |
|
Connection to SNMP |
|
To install LPSM v2.6.0, your CPU must support Advanced Vector Extensions (AVX). You can check your CPU’s AVX compatibility using the following command:
grep avx /proc/cpuinfo
If there is no output after running the command, your CPU doesn’t support AVX.
We are glad this guide helped.
Please don't include any personal information in your comment
Contact Support